-
Notifications
You must be signed in to change notification settings - Fork 54
Add week 2 blog post #1086
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add week 2 blog post #1086
Conversation
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 02s |
weekly/2026/week-2.md
Outdated
|
|
||
| ## Week 2 (January 6th – January 12th) | ||
|
|
||
| - When reporting status of a build, the related status for test job won't be reported if the labels on the PR don't match the configuration of the particular test job. ([packit-service#2928](https://github.com/packit/packit-service/pull/2928)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit hard to parse, I would probably use something like this (IIUC):
Previously, statuses were updated after a related build status update even for PR-triggered test jobs whose label requirements didn't match the PR . This has been changed in order to help avoid rate limiting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds good 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @nforro, I used your wording.
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 03s |
Signed-off-by: Marek Blaha <[email protected]>
|
Build succeeded. ✔️ pre-commit SUCCESS in 1m 03s |
|
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 1m 04s |
No description provided.